Importing the VBScript code

The Global Collaboration Framework can handle vault events two ways: with script or with the GcfEvents extension implemented in Global Collaboration Framework 2011. Both ways are supported. The script implementation is still supported for those customers that have customized GCF script and cannot use the extension. For first-time installations, we strongly recommend using the GcfEvents extension.

To make the Global Collaboration Framework VBScript functions available within the vault, you must import them into the vault's existing script.

To import the VBScript code for a first-time Global Collaboration Framework installation:

1. In Meridian Enterprise Configurator, open the vault's event procedures code for editing as described in the BlueCielo Meridian Enterprise VBScript API Reference.

2. If the following event handlers are defined:

• DocHybridEvent_BeforeHybridPart
• DocHybridEvent_AfterHybridPart

1. Merge them with the event handlers that have the same names in the new Global Collaboration Framework VBScript file <Setup>\Meridian\Configuration\MainScript.bas.

   Note    This step is unnecessary if only GCF/SharePoint is being installed. It does not support hybrid document types.

3. Copy the content of MainScript.bas to the Clipboard and paste it at the end of the vault's current event procedures code.
4. Review the list of event handlers in Suppressing custom code during Global Collaboration Framework operations and if custom event handlers exist in the vault's configuration, perform the task described in that topic.
5. Click OK to save your changes.

If a version of the Global Collaboration Framework prior to Global Collaboration Framework 2011 is already installed, you have two options:

1. Install the GcfEvents extension and remove the existing Global Collaboration Framework VBScript event handlers as described in Integrating custom Global Collaboration Framework script with Global Collaboration Framework2012 SP1. We recommend this procedure to optimize code maintenance and performance. However, it precludes customizing the Global Collaboration Framework event handlers.
2. Keep the existing (possibly customized) GCF VBScript event handlers and do not install the GcfEvents extension. However, you must also update the existing code to work with Global Collaboration Framework2012 SP1 as described in Updating custom Global Collaboration Framework script to Global Collaboration Framework2012 SP1.